fix: grouped pretty print status output #4276
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gregnr
force-pushed
the
feat/pretty-print-output
branch
from
320c852 to
ec80910
Compare
Pull Request Test Coverage Report for Build 19694860430Details
💛 - Coveralls |
gregnr
force-pushed
the
feat/pretty-print-output
branch
from
9dcaefb to
6f6c541
Compare
gregnr
force-pushed
the
feat/pretty-print-output
branch
from
6f6c541 to
3b1adbd
Compare
sweatybridge
approved these changes
Nov 26, 2025
sweatybridge
changed the title
|
Is there a way to get the old rendering of info? This makes parsing much much harder.... |
Member
Author
|
Hey @A-F-V, thanks for the heads up on docs, we'll update this. If you need to parse the info programmatically, you can use the supabase status -o env$ supabase status --help
Show status of local Supabase containers
Usage:
supabase status [flags]
Examples:
supabase status -o env --override-name api.url=NEXT_PUBLIC_SUPABASE_URL
supabase status -o json
Flags:
-h, --help help for status
--override-name strings Override specific variable names.
Global Flags:
--create-ticket create a support ticket for any CLI error
--debug output debug logs to stderr
--dns-resolver [ native | https ] lookup domain names using the specified resolver (default native)
--experimental enable experimental features
--network-id string use the specified docker network instead of a generated one
-o, --output [ env | pretty | json | toml | yaml ] output format of status variables (default pretty)
--profile string use a specific profile for connecting to Supabase API (default "supabase")
--workdir string path to a Supabase project directory
--yes answer yes to all promptsLet me know if this works for you. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This updates the pretty printed output from
supabase startandsupabase statusto be a bit more user friendly, especially for newcomers. Specifically:RESTandEdge FunctionsImplementation-wise I tried a few different table renderers (including manual), but
tablewriterended up being the most straightforward and least buggy.Testing
feat/pretty-print-output.go run . start- observe the new output.go run . statusto see the same output.